Linkset doesn't exist

I thought this impossible.  I have a links between two modules in a link module; but there is no such linkset in that module.  Cannot see it even as the "Administrator".  I can delete links.  I notice when I create a link it indeed then creates the linkset.  I notice then, of course, if I delete the linkset

What am I missing?

-Louie

Re: Linkset doesn't exist
sekrbo - Fri Sep 18 08:21:29 EDT 2015

As you said you're missing a linkset :)

I would first of all make sureI was looking in the correct link module, as it could another one with the same name but different path. I would display the qualifiedUniqueID of the link module in which the existing link is in in a trace column and then compare that to the qualifiedUniqueID of the link module in which I had been looking for the linkset... If there is a link it must be in a linkset somewhere!

Re: Linkset doesn't exist
BillTidy - Thu Oct 01 09:20:22 EDT 2015

Hi Louie

Which DOORS client version are you using? Did you copy the module that is missing the linkset? We found a feature in an earlier version where this happened - I will have to check which, I think it was one of the 9.5 versions.

Re: Linkset doesn't exist
llandale - Thu Oct 01 12:20:50 EDT 2015

I note:

• Client and Server are both v9613.
• We regularly move the entire database from a Production environment to a Development environment by shutting off the DOORS services and moving the file structure.  I note the last such move was done while the Services were v9613 but the clients remained at v9521 (for a while).
• I've logged in as the "Administrator" to insure I have suitable "R" rights.
• In the Development database I verified lots of the actual linksets (objects in link modules) are missing from the LinkModules although all the links still exist.  They are not "deleted" they are gone.
• The Production still seems to have the correct link-sets.
• We have far too many poorly written poorly tested scripts that have been hacked mercilessly (my job is to sort it out).  It is entirely plausible some script opened the source module, deleted all the links of a link-set, edited the link module, deleted the link-set, saved the link module but did not save the source module.
• However, I see no such "purge" history for the missing link-sets, although I see some for those we have mindfully purged.
• I do not believe we are archiving and then restoring anything into the Development database.

I see no loss of capability; we have lots of scripts that deal with links, they all seem to work just fine we can follow and delete them.  I notice when we create such a link it creates a linkset.